docs: add SECURITY.md security policy (#336)#732
Merged
Conversation
Add a standard security policy: private vulnerability reporting via GitHub Security Advisories, supported-version statement, and scope (model I/O readers, export artifacts). The broader OSS best-practices posture (REUSE/OpenSSF/SBOM) remains tracked by #594. Closes #336 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a standard
SECURITY.md— the security-policy slice of OSS best practices, answering #336 ("S in SKaiNET is for security?").Contents
develop(pre-1.0)The remaining OSS posture (REUSE/OpenSSF Best Practices badge, SBOM, dependency scanning) stays with #594.
Closes #336
🤖 Generated with Claude Code